-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Allow cleaning up of networks stuck in Implementing state #12409
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 4.20
Are you sure you want to change the base?
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 4.20 #12409 +/- ##
============================================
+ Coverage 16.21% 16.33% +0.11%
- Complexity 13353 13685 +332
============================================
Files 5657 5657
Lines 498647 506311 +7664
Branches 60533 63554 +3021
============================================
+ Hits 80863 82701 +1838
- Misses 408771 414434 +5663
- Partials 9013 9176 +163
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
DaanHoogland
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one nitpit, I would disect cleanupOrphanedNetworks() further as well.
| // 3) Cleanup orphaned networks stuck in Implementing state without async jobs | ||
| try { | ||
| cleanupOrphanedNetworks(); | ||
| } catch (Throwable e) { | ||
| logger.error("Unexpected exception when trying to cleanup orphaned networks", e); | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is a try catch as highest level inside cleanupOrphanedNetworks(), is this one needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just following how the other cases are handled. Also, we will be able to know which operation really failed in this block


Description
This PR fixes: #12249
This PR allows cleanup of Networks that have been stuck in Implementing state for more than the
job.expire.minutessetting and has no async jobs associated.Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?